The add-on is connected to KEDA as external-push scaler, so the polling interval isn't so relevant indeed.
When there is a change on the "active" state, the add-on pushes the change automatically, so the activation/deactivation is notified instantly. About using the polling interval to cache metrics, I don't think that HTTP Add-on metrics should be cached

I don't have in my mind all the add-on details atm, but I think that it's more or less how I have described.

Which is the goal of changing the pollingInterval value?

@JorTurFer Maybe I'm misunderstanding something, but our goal is to reduce the time of the polling interval to ensure fast scaling. Right now we solved it by not using the HTTPScaledObject and instead directly using a ScaledObject, which allows to set the polling interval. Adding this config enables us to remove that workaround.

My point is that I'm not sure if you're actually getting an advantage in the scaling or it's just a useless parameter.
For the scaling phase (1-N-1), the querying period is every 15 seconds as default (HPA default value configured at control plane level) and for the activation phase (0-1-0) I'm 99% sure that it doesn't apply because HTTP Add-on uses external-push scaler, that actively monitors the active status, scaling from 0 as soon as the http-add-on external scaler detects a single request

I mean, if you set a crazily high value (like 300 or 3000), do you need to wait up to those seconds to scale from 0 or your workload is scaled instantly? If it's scaled instantly, the pollingInterval doesn't make sense

The add-on is connected to KEDA as external-push scaler, so the polling interval isn't so relevant indeed.

Yes, omg what I was thinking before 🤦‍♂️ 😄 Too much context-switching probably.

@Spenhouet pollingInterval is not used at all by this addon, the activation happens almost immediatelly when the scaler tells KEDA to do 0->1. So this particular config doesn't affect anything.

The add-on is connected to KEDA as external-push scaler, so the polling interval isn't so relevant indeed.

yeah, that is a good point, not sure how I managed to forget this...

@Spenhouet pollingInterval is not used at all by this addon, the activation happens almost immediatelly when the scaler tells KEDA to do 0->1. So this particular config doesn't affect anything.

and given this, I think it's safe to close this PR without a merge, apologies for the confusion I caused earlier